IBIS Macromodel Task Group
Meeting date: 06 August 2024
Members (asterisk for those attending):
Achronix Semiconductor: Hansel Dsilva
Amazon: John Yan
ANSYS: * Curtis Clark
* Wei-hsing Huang
Aurora System: * Dian Yang
Raj Raghuram
Cadence Design Systems: * Ambrish Varma
Jared James
Dassault Systemes: Longfei Bai
Google: Hanfeng Wang
GaWon Kim
Intel: Michael Mirmak
Kinger Cai
Chi-te Chen
Liwei Zhao
Alaeddin Aydiner
Sai Zhou
Keysight Technologies: Fangyi Rao
Majid Ahadi Dolatsara
Stephen Slater
* Ming Yan
Rui Yang
Marvell: Steve Parker
Mathworks (SiSoft): * Walter Katz
Graham Kus
Micron Technology: Justin Butterfield
Missouri S&T: Chulsoon Hwang
Yifan Ding
Zhiping Yang
Rivos: Yansheng Wang
SAE ITC: Michael McNair
Siemens EDA (Mentor): * Arpad Muranyi
* Randy Wolff
Signal Edge Solutions Benjamin Dannan
Teraspeed Labs: [Bob Ross]
Zuken USA: Lance Wang
The meeting was led by Arpad Muranyi. Curtis Clark took the minutes.
--------------------------------------------------------------------------------
Opens:
- None.
-------------
Review of ARs:
Arpad: Share a SPICE circuit with Yifan for further study
- Done.
Arpad: Collect quotes from the specification related to [Ramp] usage for
further discussion
- Done.
--------------------------
Call for patent disclosure:
- None.
-------------------------
Review of Meeting Minutes:
Arpad asked for any comments or corrections to the minutes of the July 30th
meeting. Dian moved to approve the minutes. Curtis seconded the motion.
There were no objections.
--------------
New Discussion:
Usage In and Info (PAM4):
Walter said he wasn't sure why this is an issue at all. If an AMI parameter is
Usage In, then it's also implicitly Usage Info in that the tool can use the
information (for Reserved parameters). Arpad recalled that Michael was
concerned about possible ambiguity for some PAM4 parameters. Walter and Arpad
agreed that we should defer discussion until Michael is able to attend.
[Ramp] and Ts4file:
Walter said he didn't see a problem here. While the specification says Ts4file
is "... designed for AMI applications" and "... limited to AMI applications",
there is nothing that prevents a tool from using Ts4file data elsewhere. He
said everyone in the meeting would know how to generate a time domain waveform
with Ts4file data, and he didn't think we needed to touch any of the language in
the specification.
Arpad noted that Michael's issue was that the parser is checking [Ramp]
values for consistency with operating points computed by using the I-V tables
hooked up to the same test loads, even in the case in which Ts4file is provided
and the legacy IBIS data is supposed to be ignored. We may need to have the
parser behavior changed so that it stops checking [Ramp] vs I-V when Ts4file is
provided.
Walter said I-V and V-t tables are one view of how an IBIS model operates.
Ts4file is another view that is more amenable to LTI processing in AMI. Legacy
IBIS data is suitable for time-domain simulation but not necessarily for AMI.
Arpad and Walter agreed that we should defer discussion until Michael is able to
attend.
- Walter: Motion to adjourn.
- Ambrish: Second.
- Arpad: Thank you all for joining.
New ARs:
None.
-------------
Next meeting: 13 August 2024 12:00pm PT
-------------
IBIS Interconnect SPICE Wish List:
1) Simulator directives